dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorConfiguration in Automation Builderdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorPLC devices and componentsdl-breadcrumb-item__separatorGateway configurationdl-breadcrumb-item__separatorGateway settings on windows server
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Gateway settings on windows serverdl-permalink__symbolPermalink

Gateway as a service

To allow multiple concurrent users from different user sessions on the server to connect to PLCs, the user has to run CODESYS gateway as a system service. This is managed by a service called "CoDeSys V2.3 Gateway Service Wrapper". The service starts on system start-up and launch the gateway.

If you want to restart the gateway, use "Services management console" to restart "CoDeSys V2.3 Gateway Service Wrapper".

This executable is installed only on a windows server system and a related service (CoDeSys V2.3 Gateway Service Wrapper) is created and started.

The V3 gateway always runs as a service on windows servers and also on other Windows OS variants (e.g. Windows 10).

Gateway settings

You can set the communication settings in the Automation Builder project for every PLC. Otherwise, an error message is displayed while trying to open CODESYS.

See the description for Gateway configuration and select "TCP/IP" under “Connection”⮫ “Gateway configuration”.

Windows server usage in Automation Builder requires modifications of the system environment and of the settings in Automation Builder, e.g. permissions, licensing, session handling etc. How to setup system and software for Windows server is described in the application note ‎⮫ Windows Server 2016 - RDM access.